Repository navigation
[4.1]Run GitHub Actions on Node 24 and refresh the nvm installer - #39
Merged
antobinary merged 1 commit intoOct 21, 2026
Merged
Conversation
Move every action to the first major that runs on the node24 runtime: actions/checkout v5, setup-buildx-action v4, login-action v4 and build-push-action v7. The previous pins (checkout v3, setup-buildx v2, login v2, build-push v4) still ran on node16. Bump the nvm install script from v0.39.0 to v0.40.8 and drop the standalone "nvm use" step, which had no effect beyond its own layer; the default alias and PATH already select NODE_VERSION.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Move every action to the first major that runs on the node24 runtime: actions/checkout v5, setup-buildx-action v4, login-action v4 and build-push-action v7. The previous pins (checkout v3, setup-buildx v2, login v2, build-push v4) still ran on node16.
Bump the nvm install script from v0.39.0 to v0.40.8 and drop the standalone "nvm use" step, which had no effect beyond its own layer; the default alias and PATH already select NODE_VERSION.